Podcasting content associated with a user account

ABSTRACT

Methods, systems, and products are disclosed for podcasting content associated with a user account. Embodiments include aggregating, for a user, content of disparate data types from disparate data sources; synthesizing the aggregated content of disparate data types into a podcast capable of being rendered on a digital media player; and providing the podcast for download from a URL. Embodiments also typically include receiving a request for the podcast; and transmitting in response to the request the podcast in a response to the request.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The field of the invention is data processing, or, more specifically,methods, systems, and products for podcasting content associated with auser account.

2. Description of Related Art

Despite having more access to content from many disparate sources andhaving more disparate devices to access that content, retrieving contentfrom disparate sources with disparate devices is often cumbersome.Accessing such content is cumbersome because users typically must accesscontent of various disparate data types from various disparate datasources individually without having a single point of access foraccessing content. Content of disparate data types accessed from variousdisparate data sources often must also be rendered on data type-specificdevices using data type-specific applications without the flexibility ofrendering content on user selected devices regardless of the content'soriginal data type. There is therefore an ongoing need for consolidatedcontent management for delivery to a particular rendering device.

SUMMARY OF THE INVENTION

Methods, systems, and products are disclosed for podcasting contentassociated with a user account. Embodiments include aggregating, for auser, content of disparate data types from disparate data sources;synthesizing the aggregated content of disparate data types into apodcast capable of being rendered on a digital media player; andproviding the podcast for download from a URL. Embodiments alsotypically include receiving a request for the podcast; and transmittingin response to the request the podcast in a response to the request.

Synthesizing the aggregated content of disparate data types into apodcast for rendering on a digital media player may be carried out byselecting content for inclusion in the podcast; extracting text from theselected content; creating a media file; and storing the extracted textof the selected content as metadata associated with the media file.Synthesizing the aggregated content of disparate data types into apodcast for rendering on a digital media player may also includeextracting text from, the selected content for audio rendering in thepodcast; converting the text to speech; and recording the speech in theaudio portion of the media file. Synthesizing the aggregated content ofdisparate data types into a podcast for rendering on a digital mediaplayer may also include creating metadata describing the contentselected for inclusion in the podcast; and storing the created metadatadescribing the selected content as metadata associated with the mediafile.

The foregoing and other objects, features and advantages of theinvention will be apparent from the following more particulardescriptions of exemplary embodiments of the invention as illustrated inthe accompanying drawings wherein like reference numbers generallyrepresent like parts of exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 sets forth a network diagram illustrating an exemplary system forconsolidated content management for delivery to a rendering deviceaccording to embodiments of the present invention.

FIG. 2 sets forth a block diagram depicting a system for consolidatedcontent management for delivery to a rendering device according to ofthe present invention.

FIG. 3 sets forth a block diagram of automated computing machinerycomprising an exemplary consolidated content management server useful inconsolidated content management for delivery to a rendering deviceaccording to embodiments of the present invention.

FIG. 4 sets forth a flow chart illustrating an exemplarycomputer-implemented method for consolidated content management fordelivery to a rendering device.

FIG. 5 sets forth a flow chart illustrating an exemplary method fortransmitting requested synthesized content to a rendering device.

FIG. 6 sets forth a flow chart illustrating additional aspects ofconsolidated content management for delivery according to the presentinvention.

FIG. 7 sets forth a flow chart illustrating an exemplary computerimplemented method for aggregating content of disparate data types fromdisparate data sources for single point access by a user.

FIG. 8 sets forth a flow chart illustrating an exemplary method forestablishing a user account.

FIG. 9 sets forth a flow chart illustrating an exemplary method forestablishing a user account for the user.

FIG. 10 sets forth block diagram of exemplary user accounts containing aplurality of user account records.

FIG. 11 sets forth flow chart illustrating an exemplary method forsynthesizing content of disparate data types into synthesized contentincluding data of a uniform data type for single point access by a user.

FIG. 12 sets forth a flow chart illustrating an exemplary method fortranslating the aggregated content into text content in accordance withdevice profiles for an identified rendering device.

FIG. 13 sets forth a flow chart illustrating an exemplary method forcreating text and markup for the aggregated content in accordance withthe identified markup language.

FIG. 14 sets forth a flow chart illustrating an exemplary methodsynthesizing content of disparate data types into synthesized contentincluding data of a uniform data type single point access by a user thatincludes dynamically creating grammar sets for the text content.

FIG. 15 sets forth a flow chart illustrating an exemplary method fortranslating the aggregated content into text content in accordance withdevice profiles for an identified rendering device.

FIG. 16 sets forth a flow chart illustrating an exemplary method forsynthesizing email content into synthesized content in a media file fordelivery to a particular digital audio player for visually presentingthe email content on a display screen of the digital audio player.

FIG. 17 sets forth a block diagram of an MPEG file such as an .mp4 file.

FIG. 18 sets forth a block diagram of an AAC compressed .mp4 file suchas those supported by the iTunes digital audio player application andplayed on an iPod digital audio player.

FIG. 19 sets forth another flow chart illustrating an exemplary methodfor synthesizing email content into synthesized content in a media filefor delivery to a particular digital audio player.

FIG. 20 sets forth a flow chart illustrating an exemplary method forsynthesizing RSS content into synthesized content in a media file fordelivery to a particular digital audio player.

FIG. 21 sets forth a flow chart illustrating another exemplary methodfor synthesizing RSS content into synthesized content in a media filefor delivery to a particular digital audio player that includesconverting a portion of the RSS content to speech for audio presentationon a digital audio player.

FIG. 22 sets forth a flow chart illustrating an exemplarycomputer-implemented method for publishing content.

FIG. 23 sets forth a flow chart illustrating an exemplary method forpublishing the synthesized content through an RSS feed.

FIG. 24 sets forth a flow chart illustrating an exemplary method forpodcasting content associated with a user account.

FIG. 25 sets forth a flow chart illustrating an exemplary method forsynthesizing the aggregated content of disparate data types into apodcast for rendering on a digital media player.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS Exemplary Architecture forConsolidated Content Management

Exemplary methods, systems, and products for consolidated contentmanagement for delivery to a rendering device according to embodimentsof the present invention are described with reference to theaccompanying drawings, beginning with FIG. 1. FIG. 1 sets forth anetwork diagram illustrating an exemplary system for consolidatedcontent management for delivery to a rendering device according toembodiments of the present invention. The system of FIG. 1 operatesgenerally for consolidated content management for delivery to arendering device by aggregating, for a user, content of disparate datatypes from disparate data sources; synthesizing the aggregated contentof disparate data types into synthesized content including data of auniform data type for delivery to a particular rendering device;receiving from the rendering device a request for the synthesizedcontent; and transmitting, in a response to the request, the requestedsynthesized content to the rendering device.

Content of disparate data types are content of data of different kindand form. That is, disparate data types are data of different kinds. Thedistinctions that define the disparate data types may include adifference in data structure, file format, protocol in which the data istransmitted, application used to render the data, and other distinctionsas will occur to those of skill in the art. Examples of disparate datatypes include MPEG-1 Audio Layer 3 (‘MP3’) files, eXtensible markuplanguage documents (‘XML’), email documents, word processing documents,calendar data, and so on as will occur to those of skill in the art.Disparate data types often rendered on data type-specific devices. Forexample, an MPEG-1 Audio Layer 3 (‘MP3’) file is typically played by anMP3 player, a Wireless Markup Language (‘WML’) file is typicallyaccessed by a wireless device, and so on.

The term disparate data sources means sources of data of disparate datatypes. Such data sources may be any device or network location capableof providing access to data of a disparate data type. Examples ofdisparate data sources include servers serving up files, web sites,cellular phones, PDAs, MP3 players, and so on as will occur to those ofskill in the art.

The data processing system of FIG. 1 includes a wide area network(“WAN”) (116) including a number of disparate data sources (228)operating as disparate data sources and a consolidated contentmanagement server (114) for consolidated content management according tothe present invention. The exemplary system of FIG. 1 includes a mediaserver (230) providing content in the form of media files such as, forexample, MP3 files. The exemplary system of FIG. 1 includes an IBM OnDemand Workstation (232) a server providing support for an On DemandWorkplace (‘ODW’) that provides productivity tools, and a virtual spaceto share ideas and expertise, collaborate with others, and findinformation.

The exemplary system of FIG. 1 includes an RSS server (234) providingcontent through RSS feeds. RSS is a family of XML file formats for websyndication used by news websites and weblogs. The abbreviation is usedto refer to the following standards: Rich Site Summary (RSS 0.91), RDFSite Summary (RSS 0.9, 1.0 and 1.1), and Really Simple Syndication (RSS2.0). The RSS formats provide web content or summaries of web contenttogether with links to the full versions of the content, and othermeta-data. This content is typically delivered as an XML file called RSSfeed, webfeed, RSS stream, or RSS channel.

The system of FIG. 1 includes a calendar data server (236) thatmaintains calendar data for a user. The system of FIG. 1 also includesan email server (238).

The system of FIG. 1 includes a consolidated content management server(114). The consolidated content management server (114) providesconsolidated content management of content from the disparate datasources (228) for delivery to one or more rendering devices (104, 108,110, and 112). The consolidated content management server (114) iscapable generally of aggregating, for a user, content of disparate datatypes from disparate data sources; synthesizing the aggregated contentof disparate data types into synthesized content including data of auniform data type for delivery to a particular rendering device (104,108, 110, and 112); receiving from the rendering device (104, 108, 110,and 112) a request for the synthesized content; and transmitting, in aresponse to the request, the requested synthesized content to therendering device (104, 108, 110, and 112).

The system of FIG. 1 includes a number of rendering devices (104, 108,110, and 112) connected to a WAN (102). The rendering devices of FIG. 1include a digital audio player (‘DAP’) (104) capable of playing MP3files. An example of such a DAP is an iPod currently available fromApple. The rendering devices of FIG. 1 include smart phone (108) capableof rendering content in wireless markup language (‘WML’) and a personaldigital assistant (‘PDA’) (112) capable of rendering content in thehypertext transfer markup language (‘HTML’).

The rendering devices of FIG. 1 also include a laptop computer (110)capable of supporting a multimodal browser for rendering content inXHTML plus Voice. XHTML plus Voice (‘X+V’) is a Web markup language fordeveloping multimodal applications, by enabling voice in a presentationlayer with voice markup. X+V provides voice-based interaction in smalland mobile devices using both voice and visual elements. X+V is composedof three main standards: XHTML, VoiceXML, and XML Events. Given that theWeb application environment is event-driven, X+V incorporates theDocument Object Model (DOM) eventing framework used in the XML Eventsstandard. Using this framework, X+V defines the familiar event typesfrom HTML to create the correlation between visual and voice markup.

Each of rendering devices is capable of requesting from the consolidatedcontent management server (114) content that has been aggregated fromthe disparate data sources and synthesized into content of a uniformdata type. The consolidated content management server transmits inresponse to the request the content in a data type specific to therendering device thereby allowing the rendering device to render thecontent regardless of the native data type of content as provided by theoriginal content provider.

Consider for example, email content provided by the email server (238).The consolidated content management server (114) is capable ofaggregating for a user email content and synthesizing the email byextracting the email text and inserting the email text into a headerfield of an MP3 file. The consolidated content management server (114)transmits the MP3 file to the DAP (104) that supports the display ofinformation extracted from header fields. In this example ofconsolidated content management, the DAP (104) is capable of renderingin its display email despite being only able to render media files andwithout requiring modification of the DAP.

Consolidated content management of the present invention advantageouslyprovides a single point of access to a wide variety of content to a userand wide flexibility in the manner and upon which device that content isrendered.

The arrangement of servers and other devices making up the exemplarysystem illustrated in FIG. 1 are for explanation, not for limitation.Data processing systems useful according to various embodiments of thepresent invention may include additional servers, routers, otherdevices, and peer-to-peer architectures, not shown in FIG. 1, as willoccur to those of skill in the art. Networks in such data processingsystems may support many data communications protocols, including forexample TCP (Transmission Control Protocol), IP (Internet Protocol),HTTP (HyperText Transfer Protocol), WAP (Wireless Access Protocol), HDTP(Handheld Device Transport Protocol), and others as will occur to thoseof skill in the art. Various embodiments of the present invention may beimplemented on a variety of hardware platforms in addition to thoseillustrated in FIG. 1.

For further explanation, FIG. 2 sets forth a block diagram depicting asystem for consolidated content management for delivery to a renderingdevice according to of the present invention. The system of FIG. 2includes a plurality of rendering devices (202) for renderingsynthesized content provided by the consolidated content managementserver (114) aggregated from a plurality of disparate data sources(228). The consolidated content management server (114) is capablegenerally of aggregating, for a user, content of disparate data typesfrom disparate data sources, (230, 232), 234, 236, and 238), (228);synthesizing the aggregated content of disparate data types intosynthesized content including data of a particular data type fordelivery to a particular rendering device (104, 108, or 112); receivingfrom the rendering device (104, 108, or 112) a request for thesynthesized content; and transmitting, in a response to the request, therequested synthesized content to the rendering device (202).

The consolidated content management server (114) of FIG. 2 includes anaggregation module (208). The aggregation module (208) of FIG. 1 isimplemented as computer program instructions for aggregating data ofdisparate data types from disparate data sources. The exemplaryaggregation module (208) is capable generally of aggregating, for auser, content of disparate data types from disparate data sources byestablishing a user account for the user; retrieving content ofdisparate data types from identified disparate data sources associatedwith the user account; storing the retrieved content; and associatingthe stored content with the user account as discussed in more detailbelow with reference to FIGS. 7-10.

The consolidated content management server (114) of FIG. 2 includes asynthesis engine (212). The synthesis engine of FIG. 1 is implemented ascomputer program instructions for synthesizing aggregated content ofdisparate data types into synthesized content including data of auniform data type for delivery to a particular rendering device. Theexemplary synthesis engine (212) is capable generally of synthesizingaggregated content of disparate data types into synthesized contentincluding data of a uniform data type for delivery to a particularrendering device by identifying at least a portion of the aggregatedcontent for delivery to the particular data rendering device; andtranslating the portion of the aggregated content into text content andmarkup associated with the text content in accordance with deviceprofiles (220) for the rendering device as discussed in more detailbelow with reference to FIG. 11-14. The exemplary synthesis engine (212)is also capable generally of synthesizing aggregated content ofdisparate data types into synthesized content including data of auniform data type for delivery to a particular rendering device bycreating text in dependence upon the portion of the aggregated content;creating a media file for the synthesized content; and inserting thetext in the header of the media file as discussed in more detail belowwith reference to FIG. 15.

The consolidated content management server (114) includes repository(218) of synthesized content. Maintaining a repository (218) ofsynthesized content provides a single point of access at theconsolidated content management server for content aggregated fromvarious disparate data sources (228) for rendering on a plurality ofdisparate rendering devices (104, 108, and 112). Because the content hasbeen synthesized for delivery to the particular rendering devices (104,108, and 112) the content may be rendered in a data format that therendering devices support regardless of the original native data type ofthe content as served up by the disparate data sources (228).

Alternatively, content may be synthesized for delivery to a particularrendering device upon request for the synthesized data from a particularrendering device. Synthesizing data upon request for the data by aparticular rendering device reduces the overhead of maintaining largerepositories of synthesized content for a particular user and fordelivery to a particular device.

The consolidated content management server (114) also includes an actiongenerator (222) containing a repository of actions (224). Synthesizedcontent often has associated with it actions for execution on therendering device. For example, content synthesized as X+V documentsinclude grammars and actions providing voice navigation of the contentthereby empowering a user to use speech to instruct the rendering of thecontent on the multimodal browser of a rendering device.

Consolidated content management in accordance with the present inventionis generally implemented with computers, that is, with automatedcomputing machinery. In the systems of FIGS. 1 and 2, for example, allthe nodes, servers, and communications devices are implemented to someextent at least as computers. For further explanation, therefore, FIG. 3sets forth a block diagram of automated computing machinery comprisingan exemplary consolidated content management server (114) useful inconsolidated content management for delivery to a rendering deviceaccording to embodiments of the present invention. The consolidatedcontent management server (114) of FIG. 3 includes at least one computerprocessor (156) or ‘CPU’ as well as random access memory (168) (‘RAM’)which is connected through a system bus (160) to a processor (156) andto other components of the consolidated content management server (114).

Stored in RAM (168) is an exemplary consolidated content managementmodule (140), computer program instructions for consolidated contentmanagement for delivery to a rendering device capable of aggregating,for a user, content of disparate data types from disparate data sources;synthesizing the aggregated content of disparate data types intosynthesized content of a data type for delivery to a particularrendering device; receiving from the rendering device a request for thesynthesized content; and transmitting, in a response to the request, therequested synthesized content to the rendering device.

The consolidated content management module (140) of FIG. 2 includes anaggregation module (208) computer program instructions for aggregatingdata of disparate data types from disparate data sources. The exemplaryaggregation module (208) is capable generally of aggregating, for auser, content of disparate data types from disparate data sources byestablishing a user account for the user; retrieving content ofdisparate data types from identified disparate data sources associatedwith the user account; storing the retrieved content; and associatingthe stored content with the user account as discussed in more detailbelow with reference to FIGS. 7-10.

The consolidated content management module (140) of FIG. 2 includes asynthesis engine (212) computer program instructions for synthesizingaggregated content of disparate data types into synthesized contentincluding data of a uniform data type for delivery to a particularrendering device. The exemplary synthesis engine (212) is capablegenerally of synthesizing aggregated content of disparate data typesinto synthesized content including data of a uniform data type fordelivery to a particular rendering device by identifying at least aportion of the aggregated content for delivery to the particular datarendering device; and translating the portion of the aggregated contentinto text content and markup associated with the text content inaccordance with device profiles for the rendering device as discussed inmore detail below with reference to FIG. 11-14. The exemplary synthesisengine (212) is also capable generally of synthesizing aggregatedcontent of disparate data types into synthesized content including dataof a uniform data type for delivery to a particular rendering device bycreating text in dependence upon the portion of the aggregated content;creating a media file for the synthesized content; and inserting thetext in the header of the media file as discussed in more detail belowwith reference to FIG. 15

The consolidated content management module (140) of FIG. 3 includes anaction generator (222) computer program instructions for generatingactions associated with synthesized content. Such actions are oftenexecuted on a rendering device to whom the synthesized content istransmitted.

The exemplary consolidated content management server (114) of FIG. 3also includes a web server (155). Consolidated content management servermay usefully provide synthesized content though the use of programs thatrun on a web server and build web pages, such as for example, servlets.Such programs may build dynamic server pages such as for example JavaServer Pages (‘JSP’) containing synthesized content for delivery to aparticular rendering device. On such web server useful in consolidatedcontent management according to the present invention is the WebSpher®Application Server available from IBM. WebSphere Application Server is aJava™-based application platform, integrating enterprise data andtransactions for the dynamic e-business. WebSphere Application Serverdelivers a rich application deployment environment with applicationservices that provide transaction management, security, performance,availability, connectivity, and scalability.

Also stored in RAM (168) is an operating system (154). Operating systemsuseful in computers according to embodiments of the present inventioninclude UNIX™, Linux™, Microsoft Windows NT™, AIX™, IBM's i5/OS™, andothers as will occur to those of skill in the art.

The exemplary consolidated content management server (114) of FIG. 3includes non-volatile computer memory (166) coupled through a system bus(160) to a processor (156) and to other components of the consolidatedcontent management server (114). Non-volatile computer memory (166) maybe implemented as a hard disk drive (170), an optical disk drive (172),an electrically erasable programmable read-only memory space (so-called‘EEPROM’ or ‘Flash’ memory) (174), RAM drives (not shown), or as anyother kind of computer memory as will occur to those of skill in theart.

The exemplary consolidated content management server (114) of FIG. 3includes one or more input/output interface adapters (178). Input/outputinterface adapters in computers implement user-oriented input/outputthrough, for example, software drivers and computer hardware forcontrolling output to display devices (180) such as computer displayscreens, as well as user input from user input devices (181) such askeyboards and mice.

The exemplary consolidated content management server (114) of FIG. 3includes a communications adapter (167) for implementing datacommunications (184) with rendering devices (202). Such datacommunications may be carried out serially through RS-232 connections,through external buses such as a USB, through data communicationsnetworks such as IP networks, and in other ways as will occur to thoseof skill in the art. Communications adapters implement the hardwarelevel of data communications through which one computer sends datacommunications to another computer, directly or through a network.Examples of communications adapters useful for consolidated contentmanagement include modems for wired dial-up communications, Ethernet(IEEE 802.3) adapters for wired network communications, and 802.11 badapters for wireless network communications and other as will occur tothose of skill in the art.

Consolidated Content Management for Delivery to a Rendering Device

Consolidated content management of the present invention advantageouslyprovides a single point of access to a wide variety of content to a userand wide flexibility in the manner and upon which device that content isrendered. For further explanation, FIG. 4 sets forth a flow chartillustrating an exemplary computer-implemented method for consolidatedcontent management for delivery to a rendering device. The method ofFIG. 4 includes aggregating (402), for a user, content (404) ofdisparate data types from disparate data sources (228). Aggregated datais the accumulation, in a single location, of data of disparate types.The location of the aggregated data may be either physical, such as, forexample, on a single computer containing aggregated data, or logical,such as, for example, a single interface providing access to theaggregated data.

Aggregating (402), for a user, content (404) of disparate data typesfrom disparate data sources (228) according to the method of FIG. 4 iscarried out in dependence upon user accounts (210) established for auser that contain identifications of user selected data sources foraggregation and identifications of one or more rendering devices uponwhich synthesized content is to be rendered. Aggregating, for a user,content of disparate data types from disparate data sources may becarried out by establishing a user account for the user; retrievingcontent of disparate data types from identified disparate data sourcesassociated with the user account; storing the retrieved content; andassociating the stored content with the user account as discussed inmore detail below with reference to FIGS. 7-10.

The method of FIG. 4 also includes synthesizing (406) the aggregatedcontent (404) of disparate data types into synthesized content (408)including data of a uniform data type for delivery to a particularrendering device (202). Synthesized content is content derived fromaggregated data which has been synthesized for rendering upon aparticular rendering device. That is, the content of the aggregated datais synthesized into data of a data type that a particular renderingdevice supports.

Synthesizing aggregated content of disparate data types into synthesizedcontent including data of a uniform data type for delivery to aparticular rendering device is typically carried out in dependence upondevice profiles (220) identifying attributes of the particular renderingdevice such as file formats the device supports, markup languages thedevices supports, data communications protocols the device supports, andother attributes as will occur to those of skill in the art.Synthesizing aggregated content of disparate data types into synthesizedcontent including data of a uniform data type for delivery to aparticular rendering device may be carried out by identifying at least aportion of the aggregated content for delivery to the particular datarendering device; and translating the portion of the aggregated contentinto text content and markup associated with the text content inaccordance with device profiles for the rendering device as discussed inmore detail below with reference to FIG. 11-14.

Synthesizing the aggregated content of disparate data types intosynthesized content including data of a uniform data type for deliveryto a particular rendering device may also be carried out by creatingtext in dependence upon the portion of the aggregated content; creatinga media file for the synthesized content; and inserting the text in theheader of the media file as discussed in more detail below withreference to FIG. 15.

The method of FIG. 4 also includes receiving (410) from the renderingdevice (202) a request (412) for the synthesized content (408) andtransmitting (414), in a response (416) to the request (412), therequested synthesized content (418) to the rendering device (202). Forfurther explanation, FIG. 5 sets forth a flow chart illustrating anexemplary method for transmitting (414), in a response (416) to therequest, the requested synthesized content (418) to the rendering device(202). Transmitting (414), in a response (416) to the request, therequested synthesized content (418) to the rendering device (202)according to the method of FIG. 5 includes selecting (420) a protocol(422) for transmission to the rendering device (202) in dependence upona device profile (220) of the rendering device (202) and sending (424)the synthesized content (418) to the rendering device (202) inaccordance with the protocol (422). Protocols useful in transmittingsynthesized content to rendering devices in the Hypertext TransferProtocol (‘HTTP’), Wireless Access Protocol (‘WAP’), Handheld DeviceTransport Protocol (‘HDTP’) and many other as will occur to those ofskill in the art.

As discussed above, synthesized content often has associated with itactions for execution on the rendering device. For example, contentsynthesized as X+V documents include grammars and actions providingvoice navigation of the content thereby empowering a user to use speechto instruct the rendering of the content on the multimodal browser of arendering device. For further explanation, FIG. 6 sets forth a flowchart illustrating additional aspects of consolidated content managementfor delivery according to the present invention. The method of FIG. 6includes identifying (426) a rendering action (428) for execution by therendering device (202). An rendering action is a set of computerinstructions that when executed carry out a predefined task forrendering the synthesized content on the rendering device (202). Therendering action may be executed in dependence upon the synthesized dataimmediately or at some defined later time. Identifying (426) a renderingaction (428) may be carried out by receiving a user instruction,selecting synthesized content in response to the user instruction, andselecting particular rendering method for rendering the synthesizedcontent.

A user instruction is an event received in response to an act by a user.Exemplary user instructions include receiving events as a result of auser entering a combination of keystrokes using a keyboard or keypad,receiving speech from a user, receiving an event as a result of clickingon icons on a visual display by using a mouse, receiving an event as aresult of a user pressing an icon on a touchpad, or other userinstructions as will occur to those of skill in the art. Receiving aspeech instruction from a user may be carried out by receiving speechfrom a user, converting the speech to text, and determining independence upon the text and a grammar associated with the synthesizedcontent the user instruction.

The method of FIG. 6 also includes rendering (430) the synthesizedcontent (418), by the rendering device (202), in accordance with therendering action (426). Rendering (430) the synthesized content (418),by the rendering device (202), in accordance with the rendering action(426) result in presenting to the user (100) the synthesize contentusing the facilities supported by the rendering device. Consider forexample, email content synthesized by extracting the text from an emailand inserting the text in the header of a media file for transmission toa digital audio player. Such a player includes a display function thatdisplays text in the header of a media file which is often used todisplay metadata about a media file such as the name and artist of asong. Synthesizing the content of the email by including the text of theemail in the header of a media file advantageously allows email to berendered on the digital audio player without modification of the playeritself.

In the examples above, synthesizing the aggregated content of disparatedata types into synthesized content including data of a uniform datatype for delivery to a particular rendering device is carried out bysynthesizing the aggregated content of disparate data types intosynthesized content including data of a uniform data type for deliveryto a particular rendering device prior to receiving from the renderingdevice the request for the synthesized content. That is, content issynthesized for particular devices and stored such that the content isavailable to those particular devices. This is for explanation, and notfor limitation. In fact, alternatively synthesizing the aggregatedcontent of disparate data types into synthesized content for delivery toa particular rendering device may also be carried out by synthesizingthe aggregated content of disparate data types into synthesized contentincluding data of a uniform data type for delivery to a particularrendering device in response to receiving from the rendering device therequest for the synthesized content.

Aggregating Content of Disparate Data Types From Disparate Data Sourcesfor Single Point Access by a User

As discussed above, consolidated content management typically includesaggregating for a user, content of disparate data types from disparatedata sources. For further explanation, therefore, FIG. 7 sets forth aflow chart illustrating an exemplary computer implemented method foraggregating content of disparate data types from disparate data sourcesfor single point access by a user. The method of FIG. 7 includesestablishing (502) a user account (210) for the user (100). A useraccount (210) typically associates with a user a plurality of identifieddata sources, one or more rendering devices for rendering synthesizedcontent, and various user preferences for both synthesizing content andrendering the content.

The method of FIG. 7 also includes retrieving (508) content (404) ofdisparate data types from identified disparate data sources (228)associated with the user account (210). Retrieving (508) content (404)of disparate data types from identified disparate data sources (228)associated with the user account (210) may be carried out by retrievingthe data from memory locally, downloading the data from a networklocation, or any other way of retrieving the requested data that willoccur to those of skill in the art.

Some data sources may require security information for accessing data.Retrieving (508) content (404) of disparate data types from identifieddisparate data sources (228) associated with the user account (210) maytherefore also include determining whether the identified data sourcerequires security information to access the content and retrievingsecurity information for the data source from the user account if theidentified data source requires security information to access thecontent and presenting the security information to the data source toaccess the content.

The method of FIG. 7 also includes storing (510) the retrieved content(404) and associating (512) the stored content with the user account(210). The stored content is typically maintained in memory available toa consolidated content management server.

As discussed above, aggregating content is typically carried out independence upon a user account. For further explanation, therefore, FIG.8 sets forth a flow chart illustrating an exemplary method forestablishing a user account (210) for the user (100). The method of FIG.8 includes receiving (504), from the user (100), identifications (506)of a plurality of disparate data sources (228). Identifications (506) ofa plurality of disparate data sources (228) may include pathnames,network locations, universal resource locators (‘URLs’) uniquelyidentifying the data sources, or any other identifications of datasources that will occur to those of skill in the art.

Receiving (504), from the user (100), identifications (506) of aplurality of disparate data sources (228) may be carried out through theuse of user account configuration screens provided by a consolidatedcontent management server and accessible by a user though for example abrowser running on a rendering device. Such configuration screensprovide a vehicle for efficiently associating with a user account aplurality of disparate data sources.

The method of FIG. 8 also includes associating (507) the identifications(506) with the user account (210). Associating (507) the identifications(506) with the user account (210) may be carried out by storing theidentifications in a user record for the user in association with a userID uniquely identifying the user.

As discussed above, aggregating content is typically carried out independence upon a user account. For further explanation, FIG. 9 setsforth a flow chart illustrating an exemplary method for establishing auser account (210) for the user (100). The method of FIG. 9 includesreceiving (514), from a user, identifications (516) of one or morerendering devices (104, 106, and 112). Identifications of renderingdevices may include make and model of the rendering device, uniqueserial numbers of the rendering devices or any other identification of arendering device that will occur to those of skill in the art.

Receiving (514), from a user, identifications (516) of one or morerendering devices (104, 106, and 112) may be carried out through the useof user account configuration screens provided by a consolidated contentmanagement server and accessible by a user though for example a browserrunning on a rendering device. Such configuration screens provide avehicle for efficiently associating with a user account one or morerendering devices.

The method of FIG. 9 also includes retrieving (518) device profiles(520) for the one or more rendering devices (104, 106, and 112) independence upon the identifications (516) and associating (522) theretrieved device profiles (520) with the user account (210). Deviceprofiles (520) for the one or more rendering devices typically identifyattributes of the rendering device useful in synthesizing content forrendering on the device and for transmitting the synthesized content tothe rendering device. Examples of such attributes in devices profilesinclude markup languages supported by the device, file types supportedby the device, applications capable of being run on the device,communication protocols supported by the device and so on as will occurto those of skill in the art.

For further explanation, FIG. 10 sets forth block diagram of exemplaryuser accounts (210) containing a plurality of user account records(526). The exemplary user account records (526) include a user ID (528)uniquely identifying the user and a password (530) for authentication ofthe user in accessing the user account.

The exemplary user account records (526) include user preferences (532)for synthesizing and rendering the synthesized content for the user.Examples of such user preferences include display preferences, such asfont and color preferences, layout preferences, and so on as will occurto those of skill in the art.

The exemplary user account records (526) include a rendering device list(534) including one or more identifications of rendering devices. Theexemplary user account records (526) also includes data source list(536) including one or more identifications of disparate data sourcesand data source security information (538) including any securityinformation required to retrieve content from the identified datasource.

The information in use accounts (210) may be used to identify additionaldata sources without requiring additional user intervention. FIG. 10therefore also illustrates identifying (540) an additional data source(542) in dependence upon information in the user account. Identifying(540) an additional data source in dependence upon information in theuser account information may include identifying an additional datasource in dependence upon data sources identified by the user, renderingdevices identified by the user, user accounts for one or more otherusers, data sources identified by one or more other users, and otherinformation in user accounts as will occur to those of skill in the art.

Identifying (540) an additional data source in dependence uponinformation in the user account information may be carried out bycreating a search engine query in dependence upon the information in theuser account and querying a search engine with the created query.Querying a search engine may be carried out through the use of URLencoded data passed to a search engine through, for example, an HTTP GETor HTTP POST function. URL encoded data is data packaged in a URL fordata communications, in this case, passing a query to a search engine.In the case of HTTP communications, the HTTP GET and POST functions areoften used to transmit URL encoded data. An example of URL encoded datais:

-   -   http://www.example.com/search?field1=value1&field2=value2

This example of URL encoded data representing a query that is submittedover the web to a search engine. More specifically, the example above isa URL bearing encoded data representing a query to a search engine andthe query is the string “field1=value1&field2=value2.” The exemplaryencoding method is to string field names and field values separated by‘&’ and “=” and designate the encoding as a query by including “search”in the URL. The exemplary URL encoded search query is for explanationand not for limitation. In fact, different search engines may usedifferent syntax in representing a query in a data encoded URL andtherefore the particular syntax of the data encoding may vary accordingto the particular search engine queried.

Identifying (540) an additional data source in dependence uponinformation in the user account information may also includeidentifying, from the search results returned in the created query,additional sources of data. Such additional sources of data may beidentified from the search results by retrieving URLs to data sourcesfrom hyperlinks in a search results page returned by the search engine.

Synthesized Content for Single Point Access by a User

As discussed above, consolidated content management provides singlepoint access for content and typically includes synthesizing content ofdisparate data types into synthesized content of a uniform data type fordelivery to a particular rendering device. For further explanation, FIG.11 sets forth flow chart illustrating an exemplary method forsynthesizing content of disparate data types into synthesized contentincluding data of a uniform data type for single point access by a user.The method of FIG. 11 includes identifying (602) aggregated content(404) of disparate data types. Identifying (602) aggregated content(404) of disparate data types for synthesis may be carried out byidentifying content stored in association with a user account andaggregated for a user.

Identifying (602) aggregated content (404) of disparate data typestypically for synthesis may also be carried out in dependence upon auser instruction. That is, identifying (602) aggregated content (404) ofdisparate data types for synthesis may include receiving a userinstruction identifying aggregated content for synthesis and selectingfor synthesis the content identified in the user instruction.

The method of FIG. 11 also includes translating (604) the aggregatedcontent (404) into text content (606) in accordance with device profiles(220) for an identified rendering device (202). Translating theaggregated content into text content in accordance with device profilesfor an identified rendering device may be carried out by identifying amarkup language supported by the rendering device and creating text andmarkup for the aggregated content in accordance with the identifiedmarkup language as discussed below with reference to FIGS. 12 and 13.Translating (604) the aggregated content (404) into text content inaccordance with device profiles (220) for an identified rendering (202)device may also be carried out by creating text in dependence upon theaggregated content; creating a media file for the text content; andinserting the text in the media file as discussed below with referenceto FIG. 15.

As discussed above, translating into text content may include creatingtext and markup for the aggregated content in accordance with anidentified markup language. For further explanation, therefore, FIG. 12sets forth a flow chart illustrating an exemplary method for translatingthe aggregated content into text content in accordance with deviceprofiles for an identified rendering device that includes identifying(608) a markup language (610) supported by the rendering device (202).Identifying (608) a markup language (610) supported by the renderingdevice (202) may be carried out by retrieving a rendering device profile(220) for the rendering device and selecting a markup language supportedby the rendering device from the selected device profile. Examples ofmarkup languages useful in synthesizing aggregated content include X+V,Wireless Markup Language (‘WML’), eXtensible Markup Language (‘XML’),hypertext transfer markup language (‘HTML’) and others as will occur tothose of skill in the art.

The method of FIG. 12 also includes creating (612) text (616) and markup(618) for the aggregated content (404) in accordance with the identifiedmarkup language (610). In the example of FIG. 12, the text (616) andmarkup (618) make up a markup document (614). Creating (612) text (616)and markup (618) for the aggregated content (404) in accordance with theidentified markup language (610) includes representing in text andmarkup the aggregated content such that a browser supporting theselected markup language capable of rendering some or all of the contentcontained in the aggregated data prior to being synthesized.

Creating (612) text (616) and markup (618) for the aggregated content(404) in accordance with the identified markup language (610) such thata browser capable of rendering the text and markup may render from thetranslated content the some or all of the aggregated content prior tobeing synthesized may include augmenting the content during translationin some way. That is, translating aggregated content into text andmarkup may result in some modification to the original aggregatedcontent or may result in deletion of some content that cannot beaccurately translated. The quantity of such modification and deletionwill vary according to the type of data being translated as well asother factors as will occur to those of skill in the art.

Consider for further explanation the following markup language depictionof a snippet of audio clip describing the president.

<head> original file type=‘MP3’ keyword = ‘president’ number = ‘50’,keyword = ‘air force’ number = ‘1’ keyword = ‘white house’ number =’2’ > </head> <content> Some content about the president </content>

In the example above, an MP3 audio file is translated into text andmarkup. The header in the example above identifies the translated dataas having been translated from an MP3 audio file. The exemplary headeralso includes keywords included in the content of the translateddocument and the frequency with which those keywords appear. Theexemplary translated data also includes content identified as ‘somecontent about the president.’

As discussed above, one useful markup language for synthesizing contentis XHTML plus Voice. XHTML plus Voice (‘X+V’) is a Web markup languagefor developing multimodal applications, by enabling speech navigationand interaction through voice markup. X+V provides speech-basedinteraction in devices using both voice and visual elements. Speechenabling the synthesized data for consolidated content managementaccording to embodiments of the present invention is typically carriedout by creating grammar sets for the text of the synthesized content. Agrammar is a set of words that may be spoken, patterns in which thosewords may be spoken, or other language elements that define the speechrecognized by a speech recognition engine in a multimodal browser. Suchspeech recognition engines are useful in rendering synthesized data toprovide users with voice navigation of and voice interaction withsynthesized content.

As discussed above, synthesized content may be speech enabled. Forfurther explanation, therefore, FIG. 13 sets forth an exemplary methodsynthesizing content of disparate data types into synthesized contentincluding data of a uniform data type single point access by a user thatincludes dynamically creating (626) grammar sets (628) for the textcontent (606). As discussed above, a grammar is a set of words that maybe spoken, patterns in which those words may be spoken, or otherlanguage elements that define the speech recognized by a speechrecognition engine in a multimodal browser or other renderingapplication supported by a rendering device.

Dynamically creating grammar sets (628) for the text content (606) maybe carried out by identifying (630) keywords (632) for the text content(606). Identifying (630) keywords (632) for the text content (606) mayinclude identifying keywords in the text content (606) determinative ofcontent or logical structure and including the identified keywords in agrammar associated with the text content. Keywords determinative ofcontent are words and phrases defining the topics of the synthesizedcontent and the information presented the synthesized content. Keywordsdeterminative of logical structure are keywords that suggest the form inwhich information of the synthesized content is presented. Examples oflogical structure include typographic structure, hierarchical structure,relational structure, and other logical structures as will occur tothose of skill in the art.

Identifying keywords in the text determinative of content may be carriedout by searching the translated text for words that occur in the textmore often than some predefined threshold. The frequency of the wordexceeding the threshold indicates that the word is related to thecontent of the translated text because the predetermined threshold isestablished as a frequency of use not expected to occur by chance alone.Alternatively, a threshold may also be established as a function ratherthan a static value. In such cases, the threshold value for frequency ofa word in the translated text may be established dynamically by use of astatistical test which compares the word frequencies in the translatedtext with expected frequencies derived statistically from a much largercorpus. Such a larger corpus acts as a reference for general languageuse.

Identifying keywords in the translated text determinative of logicalstructure may be carried out by searching the translated text forpredefined words determinative of structure. Examples of such wordsdeterminative of logical structure include ‘introduction,’ ‘table ofcontents,’ ‘chapter,’ ‘stanza,’ ‘index,’ and many others as will occurto those of skill in the art.

Dynamically creating (626) grammar sets (628) for the text content (606)may also be carried out by creating (634) grammars (628) in dependenceupon the keywords (632) and grammar creation rules (636). Grammarcreation rules are a pre-defined set of instructions and grammar formfor the production of grammars. Creating grammars in dependence upon theidentified keywords and grammar creation rules may be carried out by useof scripting frameworks such as JavaServer Pages, Active Server Pages,PHP, Pern, XML from translated data. Such dynamically created grammarsmay be stored externally and referenced, in for example, X+V the<grammar src=“”/> tag that is used to reference external grammars.

The method of FIG. 13 also includes associating (640) the grammar sets(628) with the text content (606). Associating the grammar sets with thetext content includes inserting markup in a markup document containingthe translated text. Inserting markup in the markup document containingthe translate text may be carried out by creating markup defining thedynamically created grammar sets inserting the created markup into amarkup document.

The method of FIG. 13 also includes associating (642) one or moreactions (644) with the grammar sets (628). An action is a set ofcomputer instructions that when executed carry out a predefined task.Associating an action with the grammar sets thereby provides for voiceinitiation of the action such that the associated action is invoked inresponse to the recognition of one or more words or phrases of thegrammar sets.

In examples above, synthesis of the aggregated content results in thereplacement of the original aggregated content with synthesized content.This is for explanation, and not for limitation. In fact, in some casessome or all of the original aggregated content is preserved. Creatingtext and markup for the aggregated content in accordance with theidentified markup language may also be carried out by preserving thedata type of the aggregated content and also creating a markup documentfor presentation of the content in a rendering device and for invokingthe rendering of the content in the rendering device. For furtherexplanation, therefore, FIG. 14 sets forth a flow chart illustrating anexemplary method for creating (612) text (616) and markup (618) for theaggregated content (404) in accordance with the identified markuplanguage (610) that includes creating (620) a wrapper (622) for invokingthe aggregated content (404) on the rendering device (202). The wrapper(622) for invoking the aggregated content (404) on the rendering device(202) is typically a markup document created in a markup languagesupported by the rendering device for presentation of the presence ofthe content on the rendering device and for invoking the rendering ofthe content on the rendering device.

Some useful rendering devices do not support browsers for renderingmarkup documents. For example, some digital audio players play mediafiles, such as MP3 files but have no browser. For further explanation,therefore, FIG. 15 sets forth a flow chart illustrating an exemplarymethod for translating (604) the aggregated content (404) into textcontent in accordance with device profiles (220) for an identifiedrendering (202) device that does not rely on a device supporting abrowser to render a markup document. The method of FIG. 15 includescreating (646) text (648) in dependence upon the aggregated content(404). Creating (646) text (648) in dependence upon the aggregatedcontent (404) typically includes extracting or inferring text contentfrom the aggregated data for rendering on the rendering device. Forexample, the text of an email may be extracted from an email message forrendering on a digital audio player.

The method of FIG. 15 also includes creating (650) a media file (652)for the text content (648). Examples of media files include MP3 files,wav files, and others that will occur to those of skill in the art.

The method of FIG. 15 also includes inserting (654) the text (648) inthe media file (652). Media files such as, for example, MP3 filessupport header fields capable of storing the created text. Inserting(654) the text (648) in the media file (652) advantageously allows amedia player such as a digital audio player to render contentsynthesized from other data types such as email content, calendarcontent, RSS content, and other content as will occur to those of skillin the art.

Synthesizing aggregated content of disparate data types into synthesizedcontent including data of a uniform data type for delivery to aparticular rendering device according to the present invention may alsoinclude synthesizing content into synthesized content in a media filefor delivery to and rendering on a digital audio player. Synthesizingcontent of disparate data types into synthesized content in a media filefor delivery to a particular digital audio player may be carried out byretrieving content, extracting text from the retrieved content, creatinga media file and storing the extracted text as metadata associated withthe media file. Such content synthesized for delivery to a digital audioplayer may be synthesized from a variety of native data formats. Suchcontent may be email content, calendar data, RSS content, text contentin word processing documents, or any other content that will occur tothose of skill in the art.

One specific example of synthesizing content of disparate data typesinto synthesized content in a media file for delivery to a particulardigital audio player includes synthesizing email content. For furtherexplanation, FIG. 16 sets forth a flow chart illustrating an exemplarymethod for synthesizing email content into synthesized content in amedia file for delivery to a particular digital audio player forvisually presenting the email content on a display screen of the digitalaudio player. The method of FIG. 16 includes retrieving (852) an emailmessage (854). Retrieving (852) an email message (854) may be carriedout by retrieving one or more email messages from an email server (992)or retrieving one or more aggregated email messages that have beenpre-aggregated in a consolidated content management server. In theexample of FIG. 16 a consolidated content management server (114)retrieves email messages for synthesizing into a media file for deliveryto a digital audio player.

The method of FIG. 16 also includes extracting text (856) from the emailmessage (854). The principal parts of an email message are the header,the body, and any attachments to the email. The header containsinformation including sender, intended recipient, date, intendedcourtesy copy recipients, subject of the message, and others as willoccur to those of skill in the art. The body of the email messagecontains the content of the message itself. The attachments aretypically files attached to the email message. Extracting text from theemail message according to the method of FIG. 16 may include extractingtext from an email message header. Extracting text from the emailmessage according to the method of FIG. 16 may also include extractingtext from an email message body. RFC 822 outlines a standard specifyingthe syntax for messages within the framework of email.

The method of FIG. 16 also includes creating (860) a media file (810).Examples of media files include MPEG 3 (‘.mp3’) files, MPEG 4 (‘.mp4’)files, Advanced Audio Coding (‘AAC’) compressed files, AdvancesStreaming Format (‘ASF’) Files, WAV files, and many others as will occurto those of skill in the art. Creating a media file typically includescreating a media file that is supported by a digital audio player uponwhich the synthesized email is to be rendered.

The method of FIG. 16 also includes storing (868) the extracted text(858) of the email message (854) as metadata (862) associated with themedia file (810). Storing (868) the extracted text (858) of the emailmessage (854) as metadata (862) associated with the media file (810) maybe carried out by inserting the extracted text in the media file itself,such as by inserting the extracted text in an ID3 tag in an MPEG file asdiscussed below with reference to FIG. 17. Storing the extracted text ofthe email message as metadata associated with the media file may also becarried out by storing the extracted text in a metadata file associatedwith the media file such as by storing the extracted text in aneXtenxible markup language (‘XML’) library file associated with an AACcompressed MPEG 4 file as discussed below with reference to FIG. 18.

Storing (868) the extracted text (858) of the email message (854) asmetadata (862) associated with the media file (810) provides a vehiclefor visually rendering the extracted email text on a display screen of adigital audio player without modification of the digital audio player.The method of FIG. 16 therefore allows email to be rendered on a digitalaudio player that does not support displaying conventional emailmessages.

As discussed above, the extracting text from the email message may becarried out by extracting text from an email message header. Such headerinformation may be extracted and stored in association with a predefinedmetadata field supported by the digital audio player upon which theextracted text is to be rendered. Consider for further explanation thefollowing example. The identification of a sender of an email and thesubject of the email are extracted from an email message and stored asmetadata in association with a predefined metadata field for ‘Artist’and ‘Song’ supported by an iPod digital audio player. In such anexample, the extracted header information is rendered in predefinedmetadata fields on the iPod allowing a user to navigate the headerinformation of the email as the user normally navigates the metadata ofmusic files.

The extracted text from the email message may also include text from anemail message body. Such extracted text of the body may also beassociated with a predefined metadata field supported by the digitalaudio player upon which the extracted body text is to be rendered.Continuing with the example above, the extracted text from the body maybe associated in the ‘Song’ field supported by an iPod digital audioplayer. In such an example, the extracted text from the body is renderedin predefined metadata fields on the iPod when the user selects the fileassociated with the extracted body text in the same manner as a userselects a song in a media file. The user may advantageously view theemail in the display screen of the iPod.

As discussed above, storing (868) the extracted text (858) of the emailmessage (854) as metadata (862) associated with the media file (810) maybe carried out by inserting the extracted text in the media file itself,such as by inserting the extracted text in an ID3 tag in an MPEG file.For further explanation, FIG. 17 sets forth a block diagram of an MPEGfile (874) such as an .mp4 file. The MPEG file of FIG. 17 includes anaudio portion (882) of the media file. The audio portion of the MPEGfile includes the binary audio data.

The MPEG file (874) of FIG. 17 has an ID3v2 tag (878) prepended to theaudio portion (882) of the file that contains synthesized content suchas extracted email text and an image (880) such as an image extractedfrom an attachment of the email. An ID3v2 tag provides a container formetadata associated with the media file. An ID3v2 tag includes one ormore fames supporting the inclusion of text, images, files, and otherinformation. ID3v2 tags are flexible and expandable because parsers thatdo not support specific functions of the an ID3v2 tag will ignore thosefunctions. ID3v2 supports Unicode thereby providing the ability toinclude synthesized content in text of many different languages. Themaximum tag size of an ID3v2 tag is typically 256 megabytes and maximumframe size is typically 16 megabytes.

As discussed above, storing the extracted text of the email message asmetadata associated with the media file may also be carried out bystoring the extracted text in a metadata file associated with the mediafile such as by storing the extracted text in an eXtenxible markuplanguage (‘XML’) library file associated with an AAC compressed MPEG 4file. For further explanation, therefore, FIG. 18 sets forth a blockdiagram of an AAC compressed .mp4 file (884) such as those supported bythe iTunes digital audio player application and played on an iPoddigital audio player. In the example of FIG. 18, the AAC compressed .mp4file has included in the file the binary audio portion (886) of thedigital media file. The AAC compressed .mp4 file (884) of FIG. 18 alsohas an associated metadata file implemented as an eXtenxible markuplanguage (‘XML’) library file (888) that includes the synthesizedcontent as extracted text (890) from content of disparate data types.iTunes digital audio player application includes a single iTunes libraryfile that contains metadata describing the contents of the media filescomprising the iTunes library. The iTunes library file is implemented asan XML file, the format of which is defined by a flexible Document TypeDefinition (‘DTD’).

In the examples above, extracted email text is displayed on the displayscreen of a digital audio player for visual rendering of the email onthe display screen of a digital audio player. Some or all of theextracted text may also be converted to speech for audio rendering bythe digital audio player. For further explanation, FIG. 19 sets forthanother flow chart illustrating an exemplary method for synthesizingemail content into synthesized content in a media file for delivery to aparticular digital audio player. The method of FIG. 19 includesretrieving (852) an email message (854). Retrieving (852) an emailmessage (854) may be carried out by retrieving one or more emailmessages from an email server (992) or retrieving one or morepre-aggregated email messages aggregated by a consolidated contentmanagement server (114). In the example of FIG. 19 a consolidatedcontent management server (114) retrieves email messages forsynthesizing into a media file for delivery to a digital audio player.

The method of FIG. 19 also includes extracting text (856) from the emailmessage (854). As discussed above, the principal parts of an emailmessage are the header, the body, and any attachments to the email. Theheader contains information including sender, intended recipient, date,intended courtesy copy recipients, subject of the message, and others aswill occur to those of skill in the art. The body of the email messagecontains the content of the message itself. The attachments aretypically files attached to the email message. Extracting text from theemail message according to the method of FIG. 19 may include extractingtext from an email message header. Extracting text from the emailmessage according to the method of FIG. 19 may also include extractingtext from an email message body. RFC 822 outlines a standard specifyingthe syntax for messages within the framework of email.

The method of FIG. 19 also includes creating (860) a media file (810).As discussed above, examples of media files include MPEG 3 (‘.mp3’)files, MPEG 4 (‘.mp4’) files, Advanced Audio Coding (‘AAC’) compressedfiles, Advances Streaming Format (‘ASF’) Files, WAV files, and manyothers as will occur to those of skill in the art. Creating a media filetypically includes creating a media file that is supported by a digitalaudio player upon which the synthesized email is to be rendered.

The method of FIG. 19 also includes storing (868) the extracted text(858) of the email message (854) as metadata (862) associated with themedia file (810). Storing (868) the extracted text (858) of the emailmessage (854) as metadata (862) associated with the media file (810) maybe carried out by inserting the extracted text in the media file itself,such as by inserting the extracted text in an ID3 tag in an MPEG file asdiscussed below with reference to FIG. 21. Storing the extracted text ofthe email message as metadata associated with the media file may also becarried out by storing the extracted text in a metadata file associatedwith the media file such as by storing the extracted text in aneXtenxible markup language (‘XML’) library file associated with an AACcompressed MPEG 4 file as above with reference to FIGS. 17 and 18.

The method of FIG. 19 advantageously provides a vehicle for storingheader information such as the sender, intended recipient, data, time,subject and so on as metadata in the media file. Such header informationmay then be displayed visually on a display screen of digital audioplayer.

The method of FIG. 19 also provides a vehicle for storing portions ofthe email such as the body of the email in the audio portion of themedia file for audio rendering. The method of FIG. 19, therefore, alsoincludes extracting (874) text (876) from the email message (854) foraudio rendering on the digital audio player. Extracting text from theemail message according to the method of FIG. 19 may therefore alsoinclude extracting text from an email message body for audio renderingon a digital audio player.

The method of FIG. 19 also includes converting (878) the text (876) tospeech (880) and recording (870) the speech (878) in the audio portion(864) of the media file (810). Converting the text to speech andrecording the speech in the audio portion of the media file may becarried out by processing the extracted text using a text-to-speechengine in order to produce a speech presentation of the extracted emailtext and then recording the speech produced by the text-speech-engine inthe audio portion of a media file.

Examples of speech engines capable of converting extracted text tospeech for recording in the audio portion of a media filed include, forexample, IBM's ViaVoice Text-to-Speech, Acapela Multimedia TTS, AT&TNatural Voices™ Text-to-Speech Engine, and Python's pyTTS class. Each ofthese text-to-speech engines is composed of a front end that takes inputin the form of text and outputs a symbolic linguistic representation toa back end that outputs the received symbolic linguistic representationas a speech waveform.

Typically, speech synthesis engines operate by using one or more of thefollowing categories of speech synthesis: articulatory synthesis,formant synthesis, and concatenative synthesis. Articulatory synthesisuses computational biomechanical models of speech production, such asmodels for the glottis and the moving vocal tract. Typically, anarticulatory synthesizer is controlled by simulated representations ofmuscle actions of the human articulators, such as the tongue, the lips,and the glottis. Computational biomechanical models of speech productionsolve time-dependent, 3-dimensional differential equations to computethe synthetic speech output. Typically, articulatory synthesis has veryhigh computational requirements, and has lower results in terms ofnatural-sounding fluent speech than the other two methods discussedbelow.

Formant synthesis uses a set of rules for controlling a highlysimplified source-filter model that assumes that the glottal source iscompletely independent from a filter which represents the vocal tract.The filter that represents the vocal tract is determined by controlparameters such as formant frequencies and bandwidths. Each formant isassociated with a particular resonance, or peak in the filtercharacteristic, of the vocal tract. The glottal source generates eitherstylized glottal pulses for periodic sounds and generates noise foraspiration. Formant synthesis generates highly intelligible, but notcompletely natural sounding speech. However, formant synthesis has a lowmemory footprint and only moderate computational requirements.

Concatenative synthesis uses actual snippets of recorded speech that arecut from recordings and stored in an inventory or voice database, eitheras waveforms or as encoded speech. These snippets make up the elementaryspeech segments such as, for example, phones and diphones. Phones arecomposed of a vowel or a consonant, whereas diphones are composed ofphone-to-phone transitions that encompass the second half of one phoneplus the first half of the next phone. Some concatenative synthesizersuse so-called demi-syllables, in effect applying the diphone method tothe time scale of syllables. Concatenative synthesis then stringstogether, or concatenates, elementary speech segments selected from thevoice database, and, after optional decoding, outputs the resultingspeech signal. Because concatenative systems use snippets of recordedspeech, they have the highest potential for sounding like naturalspeech, but concatenative systems require large amounts of databasestorage for the voice database.

Another specific example of synthesizing content of disparate data typesinto synthesized content in a media file for delivery to a particulardigital audio player includes synthesizing RSS content. For furtherexplanation, therefore, FIG. 20 sets forth a flow chart illustrating anexemplary method for synthesizing RSS content into synthesized contentin a media file for delivery to a particular digital audio player. Themethod of FIG. 20 includes retrieving (950), through an RSS feed, RSScontent (952). Retrieving, through an RSS feed, RSS content may becarried out by invoking one or more hyperlinks provided in the RSS feedand retrieving an RSS web page or other markup document containing theRSS content.

The method of FIG. 20 also includes extracting (954) text (956) from theRSS content (952). RSS content is typically presented in a web page orother markup document accessible through a browser. Such a web page ormarkup document therefore includes display text and images for displayto a user and markup dictating the presentation of the content.Extracting text from the RSS content therefore may be carried out byretrieving display text from a web page or markup document. Suchextracted display text implements some or all of the text content of theRSS content available through the RSS feed.

The method of FIG. 20 includes creating (958) a media file (810).Examples of media files include MPEG 3 (‘.mp3’) files, MPEG 4 (‘.mp4’)files, Advanced Audio Coding (‘AAC’) compressed files, AdvancesStreaming Format (‘ASF’) Files, WAV files, and many others as will occurto those of skill in the art. Creating a media file typically includescreating a media file that is supported by a digital audio player uponwhich RSS content is to be rendered.

The method of FIG. 20 includes storing (960) the extracted text (956) ofthe RSS content (952) as metadata (862) associated with the media file(810). Storing (960) the extracted text (956) of the RSS content (952)as metadata (862) associated with the media file (810) may be carriedout by inserting the extracted text in the media file itself, such as byinserting the extracted text in an ID3 tag in an MPEG file as discussedabove with reference to FIG. 17. Storing (960) the extracted text (956)of the RSS content (952) as metadata (862) associated with the mediafile (810) may also be carried out by storing the extracted text in ametadata file associated with the media file such as by storing theextracted text in an eXtenxible markup language (‘XML’) library fileassociated with an AAC compressed MPEG 4 file as discussed above withreference to FIG. 18.

The method of FIG. 20 also includes extracting (968) one or more images(970) from the RSS content (952). As discussed above, RSS content istypically presented in a web page or other markup document accessiblethrough a browser. Such a web page or markup document therefore includesdisplay text and images for display to a user and markup dictating thepresentation of the content. Extracting (968) one or more images (970)from the RSS content (952) therefore may be carried out by retrievingimages from a web page or markup document. Such images may beimplemented as separate files referenced within the web page or markupdocument such as JPEG files, .pdf files, and others as will occur tothose of skill in the art.

The method of FIG. 20 also includes storing (962) the extracted images(970) as metadata (862) associated with the media file (810). Storing(962) the extracted images (970) as metadata (862) associated with themedia file (810) may be carried out by inserting the extracted images inthe media file itself, such as by inserting the extracted images in anID3 tag in an MPEG file as discussed above with reference to FIG. 17.Storing (962) the extracted images (970) as metadata (862) associatedwith the media file (810) may also be carried out by storing theextracted images in a metadata file associated with the media file suchas by storing the extracted text in an eXtenxible markup language(‘XML’) library file associated with an AAC compressed MPEG 4 file asdiscussed above with reference to FIG. 18.

Storing the extracted RSS text and images as metadata associated withthe media file provides a vehicle for visually rendering the extractedRSS content on a display screen of a digital audio player withoutmodification of the digital audio player. The method of FIG. 20therefore allows RSS content to be rendered on a digital audio playerthat does not support displaying conventional RSS content.

In the example of FIG. 20, text is extracted from the RSS content itselfand stored as metadata associated with the media file. In manyembodiments, text may also be extracted from the RSS feed and alsostored as metadata associated with the media file. Such extracted textmay usefully be associated with predefined metadata fields such that thesummaries and other metadata provided in the RSS feed are useful innavigating the stored RSS content on the digital audio player.

In the example of FIG. 20, text extracted from the RSS content isassociated with the media file such that the text may be displayed onthe display screen of the digital audio player. Synthesizing RSS contentfor delivery to a digital audio player may also include converting aportion of the RSS content to speech and recording the speech in theaudio portion of a media file for audio presentation of the RSS content.For further explanation, therefore, FIG. 21 sets forth a flow chartillustrating another exemplary method for synthesizing RSS content intosynthesized content in a media file (810) for delivery to a particulardigital audio player that includes converting a portion of the RSScontent to speech for audio presentation on a digital audio player. Themethod of FIG. 21 includes retrieving (950), through an RSS feed, RSScontent (952). Retrieving, through an RSS feed, RSS content may becarried out by invoking one or more hyperlinks provided in the RSS feedand retrieving an RSS web page or other markup document containing theRSS content.

The method of FIG. 21 also includes extracting (954) text (956) from theRSS content (952). RSS content is typically presented in a web page orother markup document accessible through a browser. Such a web page ormarkup document therefore includes display text and images for displayto a user and markup dictating the presentation of the content.Extracting text from the RSS content therefore may be carried out byretrieving display text from a web page or markup document. Suchextracted display text implements some or all of the text content of theRSS content available through the RSS feed.

The method of FIG. 21 includes creating (958) a media file (810).Examples of media files include MPEG 3 (‘.mp3’) files, MPEG 4 (‘.mp4’)files, Advanced Audio Coding (‘AAC’) compressed files, AdvancesStreaming Format (‘ASF’) Files, WAV files, and many others as will occurto those of skill in the art. Creating a media file typically includescreating a media file that is supported by a digital audio player uponwhich RSS content is to be rendered.

The method of FIG. 21 includes storing (960) the extracted text (956) ofthe RSS content (952) as metadata (862) associated with the media file(810). Storing (960) the extracted text (956) of the RSS content (952)as metadata (862) associated with the media file (810) may be carriedout by inserting the extracted text in the media file itself, such as byinserting the extracted text in an ID3 tag in an MPEG file as discussedabove with reference to FIG. 17. Storing (960) the extracted text (956)of the RSS content (952) as metadata (862) associated with the mediafile (810) may also be carried out by storing the extracted text in ametadata file associated with the media file such as by storing theextracted text in an eXtensible markup language (‘XML’) library fileassociated with an AAC compressed MPEG 4 file as discussed above withreference to FIG. 18.

The method of FIG. 21 also includes extracting (968) one or more images(970) from the RSS content (952). As discussed above, RSS content istypically presented in a web page or other markup document accessiblethrough a browser. Such a web page or markup document therefore includesdisplay text and images for display to a user and markup dictating thepresentation of the content. Extracting (968) one or more images (970)from the RSS content (952) therefore may be carried out by retrievingimages from a web page or markup document. Such images may beimplemented as separate files referenced within the web page or markupdocument such as JPEG files, .pdf files, and others as will occur tothose of skill in the art.

The method of FIG. 21 also includes storing (962) the extracted images(970) as metadata (862) associated with the media file (810). Storing(962) the extracted images (970) as metadata (862) associated with themedia file (810) may be carried out by inserting the extracted images inthe media file itself, such as by inserting the extracted images in anID3 tag in an MPEG file as discussed above with reference to FIG. 17.Storing (962) the extracted images (970) as metadata (862) associatedwith the media file (810) may also be carried out by storing theextracted images in a metadata file associated with the media file suchas by storing the extracted text in an eXtenxible markup language(‘XML’) library file associated with an AAC compressed MPEG 4 file asdiscussed above with reference to FIG. 18.

The RSS content synthesized according to the method of FIG. 21advantageously allows the extracted RSS text to be displayed on thedisplay screen of a digital audio player that does not support renderingconventional RSS content.

In the example of FIG. 21, text is extracted from the RSS content itselfand stored as metadata associated with the media file. In manyembodiments, text may also be extracted from the RSS feed and alsostored as metadata associated with the media file. Such extracted textmay usefully be associated with predefined metadata fields such that thesummaries and other metadata provided in the RSS feed are useful innavigating the stored RSS content on the digital audio player.

The method of FIG. 21 includes extracting (972) text (974) from the RSScontent (952) for audio rendering on the digital audio player. Asdiscussed above, RSS content is typically presented in a web page orother markup document accessible through a browser. Such a web page ormarkup document therefore includes display text and images for displayto a user and markup dictating the presentation of the content.Extracting text from the RSS content for audio rendering therefore maybe carried out by retrieving display text from a web page or markupdocument for inclusion in the audio portion of the media file and storedfor audio playback to user. Such extracted display text implements someor all of the text content accessible through the RSS feed. Examples ofextracted text usefully rendered as audio include the full body contentof the RSS content.

The method of FIG. 21 also includes converting (976) the text (974) tospeech (978) and recording (the speech in the audio portion of the mediafile. Converting (976) the text (974) to speech (978) and recording thespeech in the audio portion of the media file may be carried out byprocessing the extracted text using a text-to-speech engine in order toproduce a speech presentation of the extracted RSS content text and thenrecording the speech produced by the text-speech-engine in the audioportion of a media file as described above in discussing synthesizingemail messages.

Publishing Synthesized Content Through RSS Feeds

Consolidated content management provides a single point of access forcontent aggregated and synthesized for a user. Such content may alsoadvantageously be published. For further explanation, FIG. 22 sets fortha flow chart illustrating an exemplary computer-implemented method forpublishing content. The method of FIG. 22 includes aggregating (402),for a user, content (404) of disparate data types from disparate datasources (228). Aggregating (402), for a user, content (404) of disparatedata types from disparate data sources (228) according to the method ofFIG. 22 is carried out in dependence upon user accounts (210)established for a user that contain identifications of user selecteddata sources for aggregation and identifications of one or morerendering devices upon which synthesized content is to be rendered.Aggregating, for a user, content of disparate data types from disparatedata sources may be carried out by establishing a user account for theuser; retrieving content of disparate data types from identifieddisparate data sources associated, with the user account; storing theretrieved content; and associating the stored content with the useraccount as discussed in more detail above with reference to FIGS. 7-10.

The method of FIG. 22 also includes synthesizing (406) the aggregatedcontent (404) of disparate data types into synthesized content (408)including data of a uniform data type for delivery to a particular RSSrendering device (110). Synthesized content is content derived fromaggregated data which has been synthesized for rendering upon aparticular rendering device. That is, the content of the aggregated datais synthesized into data of a data type that a particular renderingdevice supports.

Synthesizing aggregated content of disparate data types into synthesizedcontent including data of a uniform data type for delivery to aparticular RSS rendering device is typically carried out in dependenceupon device profiles (220) for the RSS rendering device identifyingattributes of the particular rendering device such a file formats theRSS rendering device supports, markup languages the RSS rendering devicesupports, data communications protocols the RSS rendering devicesupports and other attributes as will occur to those of skill in the artas discussed above with reference to FIG. 11-14.

The method of FIG. 22 also includes publishing (702) the synthesizedcontent (408) through an RSS feed (704). An RSS feed is typicallyimplemented as one or more XML files containing summaries of web contentaccompanied by links to more extensive versions of the content at a RSScontent source, as well as other meta-data. RSS is a family of XML fileformats for web syndication used by news websites and weblogs. Theabbreviation is used to refer to the following standards: Rich SiteSummary (RSS 0.91), RDF Site Summary (RSS 0.9, 1.0 and 1.1), and ReallySimple Syndication (RSS 2.0). RSS is a format often used for syndicatingnews and the content of news-like sites, including major news sites,news-oriented community sites, and personal weblogs. RSS allows users tosee some of a web site's content, in the form of items which are createdfrom the website's associated RSS feed, without requiring the user tovisit the web site directly. If the user would like to view the fullcontent of the item, the user may activate a link to browse the websitefeaturing the full content of the channel or item.

As discussed above, an RSS feed is typically implemented as one or moreXML files containing links to more extensive versions of content. Forfurther explanation, FIG. 23 sets forth a flow chart illustrating anexemplary method for publishing the synthesized content through an RSSfeed. The method of FIG. 23 includes establishing (706) one or morehyperlinks (708) to the synthesized content, inserting (710) in an RSSfeed (704) the one or more hyperlinks (708) and associating (714) in theRSS feed (704) with each hyperlink (708) metadata (712) describing thesynthesized content accessible through the hyperlink (708). Metadata(712) describing the synthesized content accessible through thehyperlink (708) often includes summaries of the synthesized contentaccessible through the hyperlink such that a user may be informed of thesynthesized content accessible through the hyperlink.

The hyperlinks and associated metadata may provide an RSS channel tosynthesized content. An RSS channel is typically a container for anarbitrary number of items of a similar type, having some relationshipwhich is defined by the context of the container. An RSS channel tosynthesized content may be a reverse-chronological sorted list of linksto synthesized content, along with metadata describing aspects thesynthesized content story often indicating the title of content and adescription of the content.

Each RSS channel is designated by markup in the RSS feed's XML files andhas required sub-elements which are also designated by markup. Requiredsub-elements of an RSS channel typically include a title to name the RSSchannel, a link, and a description. The link is the URL of thesynthesized content typically implemented as a web page, such as, forexample, a web page written in HTML. Each RSS channel may also containoptional sub-elements. Optional sub-elements of an RSS channel include,for example, an image sub-element, which provides for an image to bedisplayed in connection with the RSS channel.

The method of FIG. 23 also includes transmitting (716) the RSS feed(704) to a rendering device (110). Transmitting (716) the RSS feed (704)to a rendering device (110) may be carried out by selecting a datacommunications protocol supported by the RSS rendering device (110) andsending the RSS feed to the RSS rendering device according to theselected data communications protocol.

The method of FIG. 23 also includes receiving (718) a request (720) forthe synthesized content through an invocation of a hyperlink (708) inthe RSS feed (704). A user may invoke a hyperlink in the RSS feedthrough, for example, a mouse or keystroke.

The method of FIG. 23 also includes sending (722) to the renderingdevice (110), in response to the request (720), a response (724)containing the synthesized content (408). Sending (722) to the renderingdevice (110), in response to the request (720), a response (724)containing the synthesized content (408) provide to a user synthesizedcontent for rendering on the RSS rendering device.

Podcasting Content Associated with a User Account

Consolidated content management according to embodiments of the presentinvention advantageously provide single point access to a wide varietyof content in a user account. Such content is often derived from data ofdisparate data types from disparate data sources. Some or all of thecontent in a user account may be usefully synthesized into a podcast andmade available for download thereby providing a vehicle for a user topublish content in the user account. Podcasting is the distribution ofmedia through audio or video files. Often podcasts contain prerecordedradio programs or music videos for rendering on mobile devices andpersonal computers. A ‘podcast’ is media file typically availablethrough a web feed. Podcasts are typically made available at a UniversalResource Locator (‘URL’) for download to the public or subscribers.

For further explanation, FIG. 24 sets forth a flow chart illustrating anexemplary method for podcasting content associated with a user account.The method of FIG. 24 includes aggregating (402), for a user, content(404) of disparate data types from disparate data sources (228).Aggregating (402), for a user, content (404) of disparate data typesfrom disparate data sources (228) according to the method of FIG. 24 istypically carried out in dependence upon user accounts established for auser that contain identifications of user selected data sources foraggregation and identifications of one or more rendering devices uponwhich synthesized content is to be rendered. Aggregating, for a user,content of disparate data types from disparate data sources may becarried out by establishing a user account for the user; retrievingcontent of disparate data types from identified disparate data sourcesassociated with the user account; storing the retrieved content; andassociating the stored content with the user account as discussed inmore detail above with reference to FIGS. 7-10.

The method of FIG. 24 also includes synthesizing (750) the aggregatedcontent (404) of disparate data types into a podcast (752) capable ofbeing rendered on a digital media player. A digital media player is anapplication capable of rendering media files. Examples of digital mediaplayers include applications running on client devices such as iTunes®from Apple®, Windows Media Player, Music Match™, and others. Digitalmedia players also include mobile devices including digital audioplayers such as, for example, the iPod® from Apple®.

Synthesizing aggregated content of disparate data types into a podcastfor rendering on a digital media player may be carried out by selectingcontent for inclusion in the podcast; extracting text from the selectedcontent; creating a media file; and storing the extracted text of theselected content as metadata associated with the media file as discussedbelow with reference to FIG. 25. Synthesizing aggregated content ofdisparate data types into a podcast for rendering on a digital mediaplayer often also includes extracting text from the selected content foraudio rendering in the podcast; converting the text to speech; andrecording the speech in the audio portion of the media file.Synthesizing aggregated content of disparate data types into a podcastfor rendering on a digital media player often also includes creatingmetadata describing the content selected for inclusion in the podcast;and storing the created metadata describing the selected content asmetadata associated with the media file.

The method of FIG. 24 also includes providing (754) the podcast (752)for download from a URL. Providing (754) the podcast (752) for downloadfrom a URL may be carried out by providing a hyperlink in a user webpageto a URL from which podcasts created for the user may be downloaded.Providing (754) the podcast (752) for download from a URL advantageouslyprovides a vehicle for publishing some or all of the content associatedwith a user account.

The method of FIG. 24 also includes receiving (756) a request (758) forthe podcast (752). In the example of FIG. 24, a request (758) for thepodcast (752) is received by a consolidated content management serversent from a digital media player (701) running on a laptop computer(110).

The method of FIG. 24 also includes transmitting (760) in response tothe request (758) the podcast in a response to the request. Transmitting(760) in response to the request (758) the podcast in a response to therequest is typically carried out according to a protocol supported bythe requestor. Protocols useful in transmitting podcasts include, forexample, HTTP (HyperText Transfer Protocol), WAP (Wireless AccessProtocol), HDTP (Handheld Device Transport Protocol), and others as willoccur to those of skill in the art. In the example of FIG. 24, therequested podcast (752) is transmitted in a response (762) to a digitalmedia player (701) running on a laptop (110).

For further explanation, FIG. 25 sets forth a flow chart illustrating anexemplary method for synthesizing the aggregated content of disparatedata types into a podcast for rendering on a digital media player. Themethod of FIG. 25 includes selecting (764) content (766) for inclusionin the podcast (752). Selecting (764) content (766) for inclusion in thepodcast (752) in the method of FIG. 25 is carried out according topredetermined content selection criteria (765). Examples ofpredetermined content selection criteria include content type, securityprotocols governing content, ownership of the content, permissionsgoverning the content, date and time of creation of the content, dateand time of aggregation of the content and many others as will occur tothose of skill in the art.

Selecting content for inclusion in the podcast may also be carried outby receiving a requestor's selection of content for inclusion in thepodcast. Such a selection may be included in a request for a podcastthat is, in fact, received prior to the podcasts creation. A requestermay be advised of content available for synthesizing into podcastthough, for example, a publication of available content on a webpage.

The method of FIG. 25 also includes extracting (768) text (784) from theselected content (766). Extracting (768) text (784) from the selectedcontent (766) may be carried out by identifying text describing theselected content or text of the content itself. Such text may beextracted from, for example, an email message header, an email messagebody, an attachment to an email, a word processing document, RSS contentavailable through an RSS feed, an RSS feed, metadata associated with amedia file, text converted from audio data stored in a media file, orany other conetn that will occur to those of skill in the art.

The method of FIG. 25 also includes creating (780) a media file (810).Examples of media files include MPEG 3 (‘.mp3’) files, MPEG 4 (‘.mp4’)files, Advanced Audio Coding (‘AAC’) compressed files, AdvancesStreaming Format (‘ASF’) Files, WAV files, and many others as will occurto those of skill in the art. Creating a media file typically includescreating a media file that is supported by a digital audio player uponwhich the synthesized email is to be rendered.

The method of FIG. 25 also includes storing (786) the extracted text(784) of the selected content (766) as metadata (862) associated withthe media file (810). Storing (786) the extracted text (784) of theselected content (766) as metadata (862) associated with the media file(810) may be carried out by inserting the extracted text in the mediafile itself, such as by inserting the extracted text in an ID3 tag in anMPEG file as discussed above with reference to FIG. 17. Storing (786)the extracted text (784) of the selected content (766) as metadata (862)associated with the media file (810) also may be carried out by storingthe extracted text in a metadata file associated with the media filesuch as by storing the extracted text in an eXtenxible markup language(‘XML’) library file associated with an AAC compressed MPEG 4 file asdiscussed above with reference to FIG. 18.

The method of FIG. 25 also includes extracting (782) text (788) from theselected content (766) for audio rendering in the podcast (752).Extracting (782) text (788) from the selected content (766) for audiorendering in the podcast (752) may be carried out by identifying textdescribing the selected content or text of the content itself. Such textmay be extracted from, for example, an email message header, an emailmessage body, an attachment to an email, a word processing document, RSScontent available through an RSS feed, an RSS feed, metadata associatedwith a media file, text converted from audio data stored in a mediafile, or any other content that will occur to those of skill in the art.

The method of FIG. 25 also includes converting (790) the text (788) tospeech (792) and recording (794) the speech (792) in the audio portion(864) of the media file (810). Converting the text to speech andrecording the speech in the audio portion of the media file may becarried out by processing the extracted text using a text-to-speechengine in order to produce a speech presentation of the extracted textand then recording the speech produced by the text-speech-engine in theaudio portion of a media file. Examples of speech engines capable ofconverting extracted text to speech for recording in the audio portionof a media filed include, for example, IBM's ViaVoice Text-to-Speech,Acapela Multimedia TTS, AT&T Natural Voices™ Text-to-Speech Engine, andPython's pyTTS class. As discussed above, each of these text-to-speechengines is composed of a front end that takes input in the form of textand outputs a symbolic linguistic representation to a back end that inturn outputs the received symbolic linguistic representation as a speechwaveform.

The method of FIG. 25 also includes creating (796) metadata (797)describing the content (766) selected for inclusion in the podcast(752). Creating (796) metadata (797) describing the content (766)selected for inclusion in the podcast (752) may be carried out byextracting existing metadata describing the content from the contentitself or from other containers such as files associated with thecontent. Alternatively, creating (796) metadata (797) describing thecontent (766) selected for inclusion in the podcast (752) may be carriedout by creating the metadata directly from the content itself such as byidentifying text describing the content. Such metadata may be createdfrom the content by extracting text such as title bars, keywords, mostcommonly used words or phrases, dates and times included in the content,the first line of text of the content, and so on as will occur to thoseof skill in the art.

The method of FIG. 25 also includes storing (798) the created metadata(797) describing the selected content (766) as metadata (797) associatedwith the media file (810). Storing (798) the created metadata (797)describing the selected content (766) as metadata (797) associated withthe media file (810) may be carried out by inserting the extracted textin the media file itself, such as by inserting the extracted text in anID3 tag in an MPEG file as discussed above with reference to FIG. 17.Storing (798) the created metadata (797) describing the selected content(766) as metadata (797) associated with the media file (810) also may becarried out by storing the extracted text in a metadata file associatedwith the media file such as by storing the extracted text in aneXtenxible markup language (‘XML’) library file associated with an AACcompressed MPEG 4 file as discussed above with reference to FIG. 18.Storing (798) the created metadata (797) describing the selected content(766) as metadata (797) associated with the media file (810) providesmetadata describing the podcast. Such metadata often accompanies apodcast such that the podcast may be distinguished from other podcastsand media files stored on a digital media player.

The examples above described content selected and stored in a singlepodcast and made available for download at a URL. This is forexplanation, and not for limitation. In fact, requestors may be providedwith options allowing requestors to receive content synthesized into aplurality of podcasts or synthesized into a single podcast.

Exemplary embodiments of the present invention are described largely inthe context of a fully functional computer system for podcasting contentassociated with a user account. Readers of skill in the art willrecognize, however, that the present invention also may be embodied in acomputer program product disposed on signal bearing media for use withany suitable data processing system. Such signal bearing media may betransmission media or recordable media for machine-readable information,including magnetic media, optical media, or other suitable media.Examples of recordable media include magnetic disks in hard drives ordiskettes, compact disks for optical drives, magnetic tape, and othersas will occur to those of skill in the art. Examples of transmissionmedia include telephone networks for voice communications and digitaldata communications networks such as, for example, Ethernets™ andnetworks that communicate with the Internet Protocol and the World WideWeb. Persons skilled in the art will immediately recognize that anycomputer system having suitable programming means will be capable ofexecuting the steps of the method of the invention as embodied in aprogram product. Persons skilled in the art will recognize immediatelythat, although some of the exemplary embodiments described in thisspecification are oriented to software installed and executing oncomputer hardware, nevertheless, alternative embodiments implemented asfirmware or as hardware are well within the scope of the presentinvention.

It will be understood from the foregoing description that modificationsand changes may be made in various embodiments of the present inventionwithout departing from its true spirit. The descriptions in thisspecification are for purposes of illustration only and are not to beconstrued in a limiting sense. The scope of the present invention islimited only by the language of the following claims.

What is claimed is:
 1. A computer-implemented method for podcastingcontent associated with a user account, the method comprising:aggregating, for a user with a digital media player, content ofdisparate data types from disparate data sources, wherein at least oneof the disparate data types is a data format that cannot be rendered bythe digital media player, and at least a portion of the content ofdisparate data types includes non-audio and non-video content;synthesizing the aggregated content of disparate data types into apodcast capable of being rendered on the digital media player, whereinthe synthesizing of the aggregated content of disparate data types intothe podcast for rendering on the digital media player further comprisesselecting content for inclusion in the podcast; extracting text from theselected content; creating a media file; and storing the extracted textof the selected content as metadata associated with the media file; andproviding the podcast for download from a URL.
 2. The method of claim 1wherein selecting content for inclusion in the podcast further comprisesreceiving a requestor's selection of content for inclusion in thepodcast.
 3. The method of claim 1 further comprising: extracting textfrom the selected content for audio rendering in the podcast; convertingthe text to speech; and recording the speech in the audio portion of themedia file.
 4. The method of claim 1 further comprising: creatingmetadata describing the content selected for inclusion in the podcast;and storing the created metadata describing the selected content asmetadata associated with the media file.
 5. The method of claim 1,further comprising: receiving a request for the podcast; andtransmitting in response to the request the podcast in a response to therequest.
 6. A computer-implemented system for podcasting contentassociated with a user account, the system comprising: a computerprocessor; a non-transitory computer memory operatively coupled to thecomputer processor; the computer memory having disposed within itcomputer program instructions capable of: aggregating, for a user with adigital media player, content of disparate data types from disparatedata sources, wherein at least one of the disparate data types is a dataformat that cannot be rendered by the digital media player, and at leasta portion of the content of disparate data types includes non-audio andnon-video content; synthesizing the aggregated content of disparate datatypes into a podcast capable of being rendered on the digital mediaplayer, wherein the synthesizing of the aggregated content of disparatedata types into the podcast for rendering on the digital media playerfurther comprises selecting content for inclusion in the podcast;extracting text from the selected content; creating a media file;storing the extracted text of the selected content as metadataassociated with the media file; and providing the podcast for downloadfrom a URL.
 7. The system of claim 6 wherein the computer memory alsohas disposed within it computer program instructions capable of:receiving a request for the podcast; and transmitting in response to therequest the podcast in a response to the request.
 8. The system of claim6 wherein computer program instructions capable of synthesizing theaggregated content of disparate data types into the podcast forrendering on a digital media player further comprise computer programinstructions capable of: selecting content for inclusion in the podcast;extracting text from the selected content; creating a media file; andstoring the extracted text of the selected content as metadataassociated with the media file.
 9. The system of claim 8 whereincomputer program instructions capable of selecting content for inclusionin the podcast further comprise computer program instructions capable ofreceiving a requestor's selection of content for inclusion in thepodcast.
 10. The system of claim 8 further comprising computer programinstructions capable of: extracting text from the selected content foraudio rendering in the podcast; converting the text to speech; andrecording the speech in the audio portion of the media file.
 11. Thesystem of claim 6 further comprising computer program instructionscapable of: creating metadata describing the content selected forinclusion in the podcast; and storing the created metadata describingthe selected content as metadata associated with the media file.
 12. Acomputer-implemented computer program product for podcasting contentassociated with a user account, the computer program product embodied ona non-transitory computer-readable recordable medium, the computerprogram product comprising: computer program instructions foraggregating, for a user with a digital media player, content ofdisparate data types from disparate data sources, wherein at least oneof the disparate data types is a data format that cannot be rendered bythe digital media player, and at least a portion of the content ofdisparate data types includes non-audio and non-video content; computerprogram instructions for synthesizing the aggregated content ofdisparate data types into a podcast capable of being rendered on thedigital media player, wherein the synthesizing of the aggregated contentof disparate data types into the podcast for rendering on the digitalmedia player further comprises computer program instructions forselecting content for inclusion in the podcast; computer programinstructions for extracting text from the selected content; computerprogram instructions for creating a media file; and computer programinstructions for storing the extracted text of the selected content asmetadata associated with the media file; and computer programinstructions for providing the podcast for download from a URL.
 13. Thecomputer program product of claim 12, further comprising: computerprogram instructions for receiving a request for the podcast; andcomputer program instructions for transmitting in response to therequest the podcast in a response to the request.
 14. The computerprogram product of claim 12, wherein computer program instructions forselecting content for inclusion in the podcast further comprise computerprogram instructions for receiving a requestor's selection of contentfor inclusion in the podcast.
 15. The computer program product of claim13, further comprising: computer program instructions for extractingtext from the selected content for audio rendering in the podcast;computer program instructions for converting the text to speech; andcomputer program instructions for recording the speech in the audioportion of the media file.
 16. The computer program product of claim 14,further comprising: computer program instructions for creating metadatadescribing the content selected for inclusion in the podcast; andcomputer program instructions for storing the created metadatadescribing the selected content as metadata associated with the mediafile.
 17. The method of claim 1, wherein the digital media player is oneof a plurality of identified rendering devices capable of rendering thepodcast, the method further comprising: maintaining a device profile foreach of the plurality of identified rendering devices, said deviceprofile specifying a supported markup language for each of the pluralityof identified rendering devices; and translating the aggregated contentinto text content in accordance with the device profile for each of theplurality of identified rendering devices.
 18. The system of claim 6,wherein the digital media player is one of a plurality of identifiedrendering devices capable of rendering the podcast, the computer memoryhaving disposed within it computer program instructions capable of:maintaining a device profile for each of the plurality of identifiedrendering devices, said device profile specifying a supported markuplanguage for each of the plurality of identified rendering devices; andtranslating the aggregated content into text content in accordance withthe device profile for each of the plurality of identified renderingdevices.
 19. The computer program product of claim 14, wherein thedigital media player is one of a plurality of identified renderingdevices capable of rendering the podcast, the computer program productfurther comprising: computer program instructions for maintaining adevice profile for each of the plurality of identified renderingdevices, said device profile specifying a supported markup language foreach of the plurality of identified rendering devices; and computerprogram instructions for translating the aggregated content into textcontent in accordance with the device profile for each of the pluralityof identified rendering devices.